fix: don't use threads for gRPC AuthMetadataPlugin, reverts #390 #467
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reverts part of #390.
grpc's documentation states AuthMetadataPlugin's
__call__
should be non-blocking. https://grpc.github.io/grpc/python/grpc.html#grpc.AuthMetadataPlugin.__call__. However, @lidiz of gRPC Python confirms that a separate thread is already spun up for the plugin callback so it will not block the gRPC call (see comment below).The current implementation of downstream clients results in threads being leaked.
Clients create gRPC channels but do not explicitly close them. See googleapis/google-cloud-python#9457 and googleapis/google-cloud-python#9790. This means associated resources do not get cleaned up.
See googleapis/google-cloud-python#9894 for an example of the changes that need to be made to downstream libraries. Also see google-api-core's
create_channel
method for resources created with a channel. Googlers, there is a detailed design doc here.Issues: